System, delivery device and methods for use therewith

ABSTRACT

A delivery device includes an image capture device for generating delivery image data of a delivery at a service address. A processor executes a delivery application to bidirectionally communicate delivery data with the delivery data server via the network interface, wherein the delivery data includes a delivery tracking number and the delivery image data. The delivery data server processes the delivery data to provide a delivery confirmation to a customer at the service address, wherein the delivery confirmation includes the delivery tracking number and the delivery image data.

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. §119(e) to U.S. Provisional Application No. 61/940,680,entitled “DELIVERY DATA SERVER AND METHODS FOR USE THEREWITH”, filedFeb. 17, 2014, which is hereby incorporated herein by reference in itsentirety and made part of the present U.S. Utility patent applicationfor all purposes.

TECHNICAL FIELD

The present disclosure relates to delivery systems used in conjunctionwith client/server network architectures.

DESCRIPTION OF RELATED ART

Some delivery companies have adopted online tools to allow customers toperform such functions as to schedule a pickup, calculate shipping fees,print shipping labels, find drop-off points, and track the status ofpackages in transit. The tracking information can indicate when apackage is been received and provide an indication of when it wasdelivered.

The limitations and disadvantages of conventional and traditionalapproaches will become apparent to one of ordinary skill in the artthrough comparison of such systems with the present invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 presents a pictorial representation of a system that includes adelivery data server 25 and example devices 13-14 that operate inaccordance with embodiments of the present disclosure.

FIG. 2 presents a block diagram representation of a delivery data server25 in accordance with an embodiment of the present disclosure.

FIG. 3 presents a block diagram representation of a client device 100 inaccordance with an embodiment of the present disclosure.

FIG. 4 presents a graphical representation of screen display 300 inaccordance with an embodiment of the present disclosure.

FIG. 5 presents a graphical representation of screen display 310 inaccordance with an embodiment of the present disclosure.

FIG. 6A presents a block diagram representation of a system thatincludes a delivery data server 25 and delivery devices 600 that operatein accordance with embodiments of the present disclosure.

FIG. 6B presents a block diagram representation of a delivery device 600in accordance with an embodiment of the present disclosure.

FIGS. 7A and 7B present graphical representations of screen displays 320and 325 in accordance with embodiments of the present disclosure.

FIG. 8 presents a graphical representation of screen display 330 inaccordance with an embodiment of the present disclosure.

FIG. 9 presents a graphical representation of screen display 340 inaccordance with an embodiment of the present disclosure.

FIG. 10 presents a graphical representation of screen display 350 inaccordance with an embodiment of the present disclosure.

FIG. 11 presents a schematic representation of delivery drone 1100 inaccordance with an embodiment of the present disclosure.

FIG. 12 presents a block diagram representation of delivery drone 1100in accordance with an embodiment of the present disclosure.

FIG. 13 presents a graphical representation of screen display 360 inaccordance with an embodiment of the present disclosure.

FIG. 14 presents a pictorial representation of delivery mat 1400 inaccordance with an embodiment of the present disclosure.

FIG. 15 presents a pictorial representation of delivery mat 1500 inaccordance with an embodiment of the present disclosure.

FIG. 16 presents a block diagram representation of beacon device 1600 inaccordance with an embodiment of the present disclosure.

FIG. 17 presents a block diagram representation of beacon device 1700 inaccordance with an embodiment of the present disclosure.

FIG. 18 presents a pictorial representation of street view 1800 inaccordance with an embodiment of the present disclosure.

FIG. 19 presents a block diagram representation of delivery drone 1100in accordance with another embodiment of the present disclosure.

FIG. 20 presents a graphical representation of screen display 2000 inaccordance with an embodiment of the present disclosure.

FIG. 21 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure.

FIG. 22 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure.

FIG. 23 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure.

FIG. 24 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure.

FIG. 25 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure.

FIG. 26 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure.

FIG. 27 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 presents a pictorial representation of a delivery data server 25and example devices 13-14 that operate in accordance with embodiments ofthe present disclosure. In particular, a delivery data server 25 ispresented that communicates with client devices such as mobile terminal13 and personal computer 14 via network 15. The network 15 can include asingle network or a plurality of different networks. These network(s)can include the Internet, a private communication network, a local areanetwork, a mobile wireless communication network, a wired or fiber opticnetwork or other broadband communication network.

The delivery data server 25 can present a website that operates via abrowser application of mobile terminal 13 and/or personal computer 14 orthat otherwise provides a server application that operates inconjunction with a client device having an application such as a mobileapplication selected for download by the user and downloaded to theclient device to present and gather delivery data that includes userdata and delivery preferences, delivery location data that indicates alocation for deliveries, delivery confirmation data and other data.

In an embodiment, a user such as a residential or business customer canregister with the delivery data server 25 to be a subscriber to enhancedservices relating to deliveries. The customer/subscriber can log intothe delivery data server 25 via an email address or other login ID, andpassword to access account information, enter preferences and paymentinformation and other information pertaining to delivery services.Delivery data in the form of service menus prompts are presented to theclient device for display relating to various information to be enteredrelating to the delivery services. In an embodiment, the delivery dataserver 25 communicates with one or more content servers 12 and otherdata servers 10 such as data servers corresponding to etailers that arethe source of goods to be delivered 10 and email server or otherelectronic messaging server that can communicate messages with theclient devices 100 or other data server. These content servers 12 caninclude a social networking server such as Facebook, MySpace, Twitter; amap server that provides map data, image data such as sky view or streetview data or other map or image data that is correlated to GPScoordinates or addresses; an advertising server; and other servers thatprovide information relating to delivery services, to other services, tocustomers, to neighborhoods, to maps and directions for locatingcustomers, and/or other content. The data servers 10 and content servers12, can each be a web server or other server that provides data to thedelivery data server 25 and/or receives data from the delivery dataserver 25. While shown as a separate device, the functionality ofdelivery data server 25 can be implemented in or on conjunction with aparticular content server 12 or data server 10 and vice versa.

In one example of operation, a client device 13 or 14 registers with thedelivery data server 25. Delivery data is communicated with the deliverydata server 25 including delivery preferences, and delivery locationdata that indicates, for example, the location at the delivery addressfor deliveries to be made. When the client devices 13 or 14 places anorder for goods with a data server 10 to be delivered via the deliverservices corresponding to delivery data server 25, and a delivery isinitiated to a corresponding subscriber, the delivery location data canbe used facilitate the delivery.

Delivery data server 25 and client devices 13 and 14 along with otherdevices and other aspects of delivery services will be described ingreater detail in conjunction with FIGS. 2-27, including severaloptional functions and features.

FIG. 2 presents a block diagram representation of a delivery data server25 in accordance with an embodiment of the present disclosure. Inparticular, delivery data server 25 includes a network interface 220such as a network card or modem for communicating with client devicessuch as client devices 13 or 14, other servers such as content servers12 and/or data servers 10 via network 15. The delivery data server 25also includes a processing module 230 and memory module 240 that storesan operating system 244 such as a Linux or Microsoft operating system orother operating system, a database 246 for storing data such as deliverydata, subscriber data, other data relating delivery services and otherdata as well as a delivery data server application 250.

The processing module 230 can be implemented via a single processingdevice or a plurality of processing devices. Such processing devices caninclude a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on operational instructions that arestored in a memory, such as memory 240. The memory can include a harddisc drive or other disc drive, read-only memory, random access memory,volatile memory, non-volatile memory, static memory, dynamic memory,flash memory, cache memory, and/or any device that stores digitalinformation. Note that when a processing device implements one or moreof its functions via a state machine, analog circuitry, digitalcircuitry, and/or logic circuitry, the memory storing the correspondingoperational instructions may be embedded within, or external to, thecircuitry comprising the state machine, analog circuitry, digitalcircuitry, and/or logic circuitry. While a particular bus architectureis presented that includes a single bus 260, other architectures arepossible including additional data buses and/or direct connectivitybetween one or more elements. Further, the delivery data server 25 caninclude one or more additional elements that are not specifically shown.

At least one processor of the processing module 230 executes thedelivery data server application 250 to bidirectionally communicatedelivery data with a user of a client device, such as client device 13or 14 via the network interface 220 and the network 15. In operation,the delivery data server application 250 sends delivery data in the formof delivery menu data, or prompts or other data to a client device, suchas client device 13 or 14, via the network 15. The delivery menu datacan include screen displays and prompts for the user of client device 13or 14 to make menu selections to enter text or media or to otherwiseinteract with the client device 13 or 14 to gather delivery data that issent to the delivery data server 25. The delivery menu data can alsoinclude screen displays that provide other information to client device13 or 14 or other data communications between the delivery data server25 and the client device 13 or 14.

In one mode of operation, the processing module 230 executes thedelivery data server application 250 to bidirectionally communicatedelivery data with a user of a client device 13 or 14 via the networkinterface 220. The delivery data includes delivery menu data sent to theclient device 13 or 14 that prompts the user to enter delivery locationdata that indicates a service address associated with a user of thefirst client device and a delivery location associated with the serviceaddress for receiving at least one delivery to the service address. Thedelivery location data indicated by the user is received from the clientdevice 13 or 14 via the network interface 220.

The operation of delivery data server 25 in generating and responding todelivery data will be described in greater detail in conjunction withFIGS. 3-27, including several optional functions and features and otheraspects of one or more delivery services.

FIG. 3 presents a block diagram representation of a client device 100 inaccordance with an embodiment of the present disclosure. In particular,a client device 100, such as mobile terminal 13, personal computer 14 orother client device such as a personal digital assistant, e-reader,tablet, or smartphone is presented. The client device 100 includes anetwork interface 120 having one or more interfaces (122, 124 . . . ).Examples of interfaces (122, 124 . . . ) include wireless interfacessuch as a 3G, 4G or other wireless telephony transceiver, a Bluetoothtransceiver, a WiFi transceiver, UltraWideBand transceiver, WIMAXtransceiver, ZigBee transceiver or other wireless interface. Examples ofinterfaces (122, 124 . . . ) further include wired interfaces such as aUniversal Serial Bus (USB) interface, an IEEE 1394 Firewire interface,an Ethernet interface or other network card or modem for communicatingwith delivery data server 25, or other servers such as content servers12 via network 15. The client device 100 also includes a user interface142 such as a display device, touch screen, key pad, touch pad, thumbwheel, one or more buttons, a speaker, a microphone, an accelerometer,gyroscope or other motion or position sensor, or other interface devicesthat provide information to a user of the client device 100 and thatgenerate data in response to the user's interaction with the clientdevice 100. In addition, the client device 100 includes an image capturedevice 146 such as a digital camera that captures still or video imageswith or without associated audio.

The client device 100 also includes a processing module 130 and memorymodule 140 that stores an operating system 44 such as a Linux-basedoperating system, a Microsoft personal computer or mobile operatingsystem, an Android operating system, an Apple mobile or personalcomputer operating system or other operating system. The memory module140 also stores location data 42 corresponding to the location of theclient device 100 generated via user interaction with user interface142, via optional Global Positioning System (GPS) receiver 144, one ormore motion sensors such as accelerometers, gyroscopes or other sensors,or gathered via a wireless network such as triangulation data receivedfrom a 4G network, location information from a connected access point orbase station, femtocell or other location data. In addition, memorymodule 140 includes a messaging application 46 for communicating withother client devices such as an email application, a text, instantmessaging or short messaging service (SMS) application or othermessaging application that stored contacts data corresponding to usersof other client devices that are known to the user of client device 100as well as contact information corresponding to message recipients.

The memory module 140 also stores a delivery data client application 150that is prestored in the memory module, loaded via disk or downloaded tothe memory module via network interface 120. The delivery data clientapplication 150 can be a general browser application such as Mozilla,Google Chrome, Safari, Internet Explorer or other general web browser oran application that is customized to operate in conjunction withdelivery data server 25 in conjunction with the exchange of deliverydata.

The processing module 130 can be implemented via a single processingdevice or a plurality of processing devices. Such processing devices caninclude a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on operational instructions that arestored in a memory of memory module 140. The memory can include a harddisc drive or other disc drive, read-only memory, random access memory,volatile memory, non-volatile memory, static memory, dynamic memory,flash memory, cache memory, and/or any device that stores digitalinformation. Note that when the processing device implements one or moreof its functions via a state machine, analog circuitry, digitalcircuitry, and/or logic circuitry, the memory storing the correspondingoperational instructions may be embedded within, or external to, thecircuitry comprising the state machine, analog circuitry, digitalcircuitry, and/or logic circuitry. While a particular bus architectureis presented that includes a single bus 160, other architectures arepossible including additional data buses and/or direct connectivitybetween one or more elements. Further, the client device 100 can includeone or more additional elements that are not specifically shown.

The operation of client device in generating and responding to deliverydata will be described in greater detail in conjunction with FIGS. 4-27,including several optional functions and features and other aspects ofone or more delivery services.

FIG. 4 presents a graphical representation of screen display 300 inaccordance with an embodiment of the present disclosure. In particular,a screen display 300 of user interface 142 of client device 100 ispresented as generated by the delivery data client application 150 inresponse to delivery data from the delivery data server application 250.As shown, a user, “Bob Robertson” has logged in. This login can, forexample, be based on the entry of a username and password, based on acookie file retrieved from the memory module 240 of the client device100 or based on other subscription information or authenticationprocedures.

Delivery location data received from the client device 100 indicates aservice address associated with a user of the first client device and adelivery location associated with the service address for receiving atleast one delivery to the service address. The screen display 300 is onein a number of different screen displays that guide the user in enteringdelivery location data and other data relating to delivery services forthe user in conjunction with either a particular delivery or withrespect to one or more future deliveries at a particular serviceaddress.

The screen display 300 includes an ad 302 generated based on data fromcontent server 12, and optionally based on location data 42 receivedfrom client device 100 via the network 15 and/or user profile datarelating to the user of client device 100 stored in conjunction withuser's subscription. In a mode of operation, the ad 302 presents anadvertisement pertaining to products or services local to the user andfurther based on profile data, demographic data or user preferences.

Section 304 provides a graphical user interface for the user to entercustomer information in the form of name data that indicates the name ornames of customer(s) at the service address and/or service address datathat indicates a delivery address where goods are to be delivered by oneor more delivery services. Section 306 provides a graphical userinterface for the user to enter delivery location data such as aselection of one or more of a plurality of different descriptors ofpossible delivery locations.

Section 308 provides a graphical user interface for the user to select aspecific view type. This selection can be used in a mode of operationwhere image data corresponding to the delivery address is used togenerate location data indicating a one or more delivery locationscorresponding to the delivery address. In the embodiment shown, the usercan select a street view, sky view or other view such as one or moreside views, a back view such as a backyard view of a residential addressor other view of the property at the delivery address.

Section 308 also provides a graphical user interface for the user toselect a specific delivery type such as deliveries associatedexclusively with one or more specific tracking numbers, all delivers tothe service address, weekday deliveries, daylight deliveries, etc. Whileparticular options are presented, other delivery types such as weekenddeliveries, night time deliveries, differentiation of deliveries by timeof day, size and/or shape of the package, value of the package, the dayof the week or other delivery types can also be used. Further, differentdelivery locations can be indicated and stored in a subscriber profilebased on the differing delivery types. When a particular deliverycorresponding to a delivery type occurs, the delivery service canrespond by delivering the package to the location indicated by thedelivery type. For example, packages having one or more dimensions thatare larger than a dimension threshold can have one selected deliverylocation while packages not having one or more dimensions that arelarger than a dimension threshold can have another selected deliverylocation. Weekend and weekday deliveries can correspond to differentdelivery locations. Packages of differing declared values or differinginsured values can be assigned to differing locations, etc.

It should be noted that the particular menu structure, screen layout andoptions are merely illustrative of the many types of delivery data thatcan be presented and could be selected in accordance with variousembodiments of the present disclosure.

In the example shown the names and delivery address have been entered insection 304, a front door delivery location has been selected in section306, a street view type has been selected along with a delivery type ofall deliveries. A next button 316 is presented that, when selected bythe user, sends the delivery data entered by the user in accordance withthis screen display to the delivery data server 25 via the network 15.In response, the delivery data server 25 can send a new screen displaythat, if applicable, includes delivery data with additional menu data.

FIG. 5 presents a graphical representation of screen display 310 inaccordance with an embodiment of the present disclosure. In particular,a screen display 310 of user interface 142 of client device 100 ispresented as generated by the delivery data client application 150 inresponse to delivery data from the delivery data server application 250.Common elements from other figures may be indicated by common referencenumerals. The screen display 310 is one in a number of different screendisplays that guide the user in entering delivery data relating todeliveries to a particular service address.

Delivery location data received from the client device 100 is generatedat the client device 100 based on a user selection of the deliverylocation in relation to the captured image data corresponding to thedelivery address. The delivery location data is sent to the deliverydata server 25. The delivery data server application 250 processes thedelivery location data to direct one or more deliveries to the serviceaddress. In particular captured image data and/or other deliverylocation data can be used by delivery personnel to place a delivery in adesired delivery location.

The screen display 310 follows an example presented in conjunction withFIG. 4 where a street view was selected by the user and where image datacorresponding to the delivery address is used to generate location dataindicating a one or more delivery locations corresponding to thedelivery address. In the example shown, an image of a street view 314along with an indication of the delivery address 312 is presented to theuser.

In an embodiment, the street view is either retrieved from a database246 of the delivery data server 25 or from a content server 12 thatprovides captured image data for different street addresses. In thiscase, the street address entered by the user in conjunction with displayscreen 300 is used, along with the selection of street view type toretrieve particular street view image data corresponding to the deliveryaddress. In another embodiment, an image capture device such as a cameraintegrated with the client device 100 or other digital camera in use bythe user can be used to capture the street view image data.

In the example shown, the client device 100 generates the deliverylocation in relation to the captured image data corresponding to thedelivery address based on a superposition of a delivery location icon316 on the captured image data 314 corresponding to the deliveryaddress. When the captured image data 314 of the street viewcorresponding to the delivery address is displayed, the user can adjustthe position of the delivery location icon 316 via interaction with amouse, other pointing device or other user interface until the positionof the delivery location icon 316 on the captured image data 314corresponds to the desired delivery location. In the example shown, theuser has moved the delivery location icon 316 to a position just to theright of the front door.

Delivery location data that includes the superposition of the deliverylocation icon 316 on the captured image data 314 is sent to the deliverydata server 25 for use by a delivery service person in determining thesubscribers desired delivery location. In one mode of operation, thedelivery location data is sent to a delivery device associated with adelivery service person. The delivery device displays the superpositionof the delivery location icon on the captured image data correspondingto the delivery address to aid the delivery service person indetermining the subscribers desired delivery location for a package.

While the example described above has focused on a street view, otherviews of the property at the delivery address can likewise be employed.In another example, a sky view can be either retrieved from a database246 of the delivery data server 25 or from a content server 12 thatprovides captured image data, such as satellite or drone imagery fordifferent street addresses. In this case, the street address entered bythe user in conjunction with display screen 300 is used, along with theselection of street view type to retrieve particular sky view image datacorresponding to the delivery address. In a further example, an imagecapture device such as a camera integrated with the client device 100 orother digital camera in use by the user can be used to capture backyardor side view image data corresponding to the delivery address.

In the example shown, the delivery location data includes, in additionor in the alternative, GPS coordinates selected by the client device100. These GPS coordinates can be generated in different ways. In anembodiment, the client device 100 can be placed at delivery location andthe GPS coordinates can be determined by the GPS receiver 144 andcaptured by the delivery data client application 150 for display ondisplay 310 and inclusion in the location data sent to the delivery dataserver 25.

In another embodiment, the GPS coordinates can be calculated inconjunction with the positioning of the delivery location icon 316 onthe captured image data 314. Consider an example where the capturedimage data corresponds to a rectangular sky view of the deliveryaddress. Each of the four corners of the sky view can have correspondingGPS coordinates. The positioning of the delivery location icon 316 onthe captured image data 314 can be used to generate the GPS coordinatesof the desired delivery location by correlating the pixel coordinates ofthe corners to the GPS coordinates of the corners and by interpolation,based on the pixel coordinates of the delivery location icon 316.

In an embodiment, the positioning of the delivery location icon 316 onthe captured image data 314 may be restricted to certain areas of thecaptured image data 314. Consider an example where the captured imagedata 314 corresponds to a street view. In this case, the positioning ofthe delivery location icon 316 may be limited to correspond to a groundlevel and not an above-ground location. Consider an example where thecaptured image data 314 corresponds to a sky view. In this case, thepositioning of the delivery location icon 316 may be restricted toexclude a roof location, a location corresponding to a pool or locationscorresponding to trees, gardens other landscaping or other undesirabledelivery locations. In an embodiment, if a restricted delivery locationis selected, delivery data can be generated by the delivery data server25 to indicate that a prior selection corresponded to a restrictedlocation and re-prompt to user to select a new location. In anotherembodiment, the delivery data client application 150 can receiveinformation relating to allowed or restricted areas and either indicatethese restricted areas and/or only allow placement of the deliverylocation icon 316 in permitted areas.

While an example format for delivery location icon 316 is presented,other delivery location icons including other text, no text, and/orgraphic images can likewise be implemented. In an embodiment where thedelivery location is being generated based on a particular shipment andinformation regarding the package size and/or shape is available inconjunction with the particular shipment, the size of the deliverylocation icon 316 can be sized and/or presented to scale in conjunctionwith the captured image data 314 to represent the actual size and/orshape of the particular package to be delivered. In this fashion, theuser of client device 100 can select a delivery location based on theactual size and shape of a particular package to be delivered.

FIG. 6A presents a block diagram representation of a system thatincludes a delivery data server 25 and delivery devices 600 that operatein accordance with embodiments of the present disclosure. The deliverydevices 600 are each capable of bidirectional communication with thedelivery data server 25 via network 15. Each delivery device 600 can beimplemented via a handheld communication device that is used by deliveryservice personnel (the user) in conjunction with a delivery of a packageor other goods.

In addition to receiving delivery location data from delivery dataserver 25 that was generated via interactions with a client device 100,the delivery devices 600 can exchange other delivery data with deliverydata server 25 for facilitating deliveries or otherwise providingdelivery services to different service addresses.

FIG. 6B presents a block diagram representation of a delivery device 600in accordance with an embodiment of the present disclosure. The deliverydevice 600 includes many common functions and features of client device100 described in conjunction with FIG. 3 that are referred to by commonreference numerals. In particular, a delivery device 600, such as amobile terminal, personal computer, personal digital assistant, tablet,or smartphone or other delivery device is presented for use by deliveryservice personnel (the user) in conjunction with a delivery of a packageor other goods.

The delivery device 600 includes a network interface 120 having one ormore interfaces (122, 124 . . . ). Examples of interfaces (122, 124 . .. ) include wireless interfaces such as a 3G, 4G or other wirelesstelephony transceiver, a Bluetooth transceiver, a WiFi transceiver,UltraWideBand transceiver, WIMAX transceiver, ZigBee transceiver orother wireless interface. Examples of interfaces (122, 124 . . . )further include wired interfaces such as a Universal Serial Bus (USB)interface, an IEEE 1394 Firewire interface, an Ethernet interface orother network card or modem for communicating with delivery data server25, or other servers such as content servers 12 via network 15. Thedelivery device 600 also includes a user interface 142 such as a displaydevice, touch screen, key pad, touch pad, thumb wheel, one or morebuttons, a speaker, a microphone, an accelerometer, gyroscope or othermotion or position sensor, or other interface devices that provideinformation to a user of the delivery device 600 and that generate datain response to the user's interaction with the delivery device 600. Inaddition, the delivery device 600 includes an image capture device suchas a digital camera that captures still or video images with or withoutassociated audio.

The delivery device 600 also includes a processing module 130 and memorymodule 140 that stores an operating system 44 such as a Linux-basedoperating system, a Microsoft personal computer or mobile operatingsystem, an Android operating system, an Apple mobile or personalcomputer operating system or other operating system. The memory module140 also stores location data 42 corresponding to the location of theclient device delivery device 600 generated via user interaction withuser interface 142, via optional Global Positioning System (GPS)receiver 144, or gathered via a wireless network such as triangulationdata received from a 4G network, location information from a connectedaccess point or base station, femtocell or other location data. Inaddition, memory module 140 includes a messaging application 46 forcommunicating with other client devices such as an email application, atext, instant messaging or short messaging service (SMS) application orother messaging application that stored contacts data corresponding tousers of other delivery devices 600.

The memory module 140 also stores a delivery application 650 that isprestored in the memory module, loaded via disk or downloaded to thememory module via network interface 120. The delivery application 650can be a general browser application such as Mozilla, Google Chrome,Safari, Internet Explorer or other general web browser or an applicationthat is customized to operate in conjunction with delivery data server25. The processing module 130 executes the delivery application 650 tobidirectionally communicate delivery data with a delivery data server 25via the network interface 120. In addition to receiving deliverylocation data from delivery data server 25 that was generated viainteractions with a client device 100, the delivery devices 600 canexchange other delivery data with delivery data server 25 forfacilitating deliveries and providing delivery services to differentservice addresses.

The processing module 130 can be implemented via a single processingdevice or a plurality of processing devices. Such processing devices caninclude a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on operational instructions that arestored in a memory of memory module 140. The memory can include a harddisc drive or other disc drive, read-only memory, random access memory,volatile memory, non-volatile memory, static memory, dynamic memory,flash memory, cache memory, and/or any device that stores digitalinformation. Note that when the processing device implements one or moreof its functions via a state machine, analog circuitry, digitalcircuitry, and/or logic circuitry, the memory storing the correspondingoperational instructions may be embedded within, or external to, thecircuitry comprising the state machine, analog circuitry, digitalcircuitry, and/or logic circuitry. While a particular bus architectureis presented that includes a single bus 160, other architectures arepossible including additional data buses and/or direct connectivitybetween one or more elements. Further, the delivery device 600 caninclude one or more additional elements that are not specifically shown.

In an embodiment, the delivery data received from the delivery dataserver 25 includes delivery location data generated by a client devicethat indicates a service address associated with a user of the clientdevice 100 and a delivery location associated with the service addressfor receiving at least one delivery to the service address. Aspreviously discussed, the delivery location data can indicate a userselection of the delivery location in relation to captured image datacorresponding to the delivery address. Further, the delivery locationdata can indicate the user selection of the delivery location bysuperposition of a delivery location icon on the captured image datacorresponding to the delivery address. In one mode of operation, adisplay device included in the user interface 142 displays thesuperposition of the delivery location icon on the captured image datacorresponding to the delivery address to aid the delivery service personin identifying the location at the service address to place the packageor other delivery.

In another mode of operation, the image capture device 146 captures alive image of the property at the delivery address. The display deviceof user interface 142 displays a superposition of a delivery locationicon on the live image corresponding to the delivery address. Thedelivery application 650 uses augmented reality techniques to adjust theposition of the delivery location icon on the live image to correspondto the delivery location. In an embodiment, the delivery application 650uses image recognition to correlate the captured live image data toimage data that includes the delivery location icon received vialocation data exchanged between the delivery data server 25 and a clientdevice 100. Portions of the captured live image data that contain thesame scene as indicated in the image data of the delivery location dataare identified, scaled to match the captured live image data and theposition is tracked. The delivery application 650 generates its owndelivery location icon that is superimposed in the captured live imagedata at the proper location corresponding to where the user of theclient device placed his or her own delivery location icon 316 in theimage 314. In an alternative embodiment, the position and currentviewing orientation of the delivery device 600 are determined based onthe GPS receiver 144 and/or other position and motion sensors or otherposition and orientation data generated by the delivery device 600. Thisposition and current viewing orientation are used in conjunction withdelivery location data indicating the subscriber's delivery location toadjust the position of a delivery location icon for superposition withthe captured live image data.

In an embodiment, the image capture device 146 generates delivery imagedata of a delivery of the package or other goods at a service address.The memory stores the delivery image data. The delivery data includes adelivery tracking number for a particular delivery along with thedelivery image data. The delivery data server 25 receives the deliverydata and processes the delivery data to provide a delivery confirmationto a customer at the service address that includes the delivery trackingnumber and the delivery image data.

The operation of the delivery device 600 in generating and responding todelivery data will be described in greater detail in conjunction withFIGS. 7-27, including several optional functions and features and otheraspects of one or more delivery services.

FIGS. 7A and 7B present graphical representations of screen displays 320and 325 in accordance with embodiments of the present disclosure. Inparticular, screen displays 320 and 325 of user interface 142 ofdelivery device 600 are presented as generated by the deliveryapplication 650 in response to delivery data from the delivery dataserver application 250. Common elements from other figures may beindicated by common reference numerals. The screen displays 320 and 325are used to guide service personnel in delivering a package or othergoods to a delivery location at a particular service address.

As shown in screen display 320, a service person, “Delivery Driver#4321” has logged in. This login can, for example, be based on the entryof a username and password, based on a cookie file retrieved from thememory module 240 of the delivery device 600, based on the use of asecure ID token or based on other subscription information orauthentication procedures.

The section 322 includes the service address and the package trackingnumber. As discussed in conjunction with FIG. 6B, delivery location datafrom a client device 100 can indicate a user selection of the deliverylocation in relation to captured image data corresponding to thedelivery address by superposition of a delivery location icon on thecaptured image data corresponding to the delivery address. Screendisplay 320 presents an example where the user of the delivery device600 has selected a stored view in region 328. In this mode of operation,the delivery device 600 receives static image data via the delivery dataserver 25 as selected by the client device 100. The image data includesa static image 323 that includes the superposition of the deliverylocation icon 326 on a view of the delivery address that was eithercaptured by the client device 100 or forwarded to the client device 100via the delivery server 25. The delivery person can refer to the staticimage 323 selected by the subscriber in determining where to place thepackage.

Screen display 325 presents an example where the user of the deliverydevice 600 has selected a live view in region 328. In this mode ofoperation, the delivery device 600 captures a live image 324 of theproperty at the delivery address. The delivery device 600 displays asuperposition of a delivery location icon 326 on the live imagecorresponding to the delivery address. The delivery device 600 usesaugmented reality techniques to adjust the position of the deliverylocation icon on the live image to correspond to the delivery location.The delivery person can scan the live image 324 at differentorientations at the service address to find the delivery location icon326 in order to determine where to place the package.

FIG. 8 presents a graphical representation of screen display 330 inaccordance with an embodiment of the present disclosure. In particular,a screen display 330 of user interface 142 of delivery device 600 ispresented as generated by the delivery application 650 in response todelivery data from the delivery data server application 250. Commonelements from other figures may be indicated by common referencenumerals. The screen display 320 is used by service personnel indelivering a package or other goods to a delivery location at aparticular service address.

In particular, region 334 displays a live image of the delivery of apackage 336 at a delivery address generated by image capture device 146of delivery device 600. When a package is delivered the service personcaptures the image 334 showing the delivery by selecting the capturebutton 338. The image capture device 146 generates delivery image dataof a delivery at a service address corresponding to the image displayedin region 334. A shown, the live image 334 can include the current dataand time and the captured images can reflect the date and time thedelivery image was captured—corresponding to the date and time ofdelivery.

In operation, the memory module 140 of delivery device 600 stores thedelivery image data and the processing module 130 operates inconjunction with the network interface 120 to send the delivery imagedata and other information such as the date and time of the delivery, atracking number associated with the delivery and/or other data to thedelivery data server 25. The delivery data server 25 processes thedelivery data to provide a delivery confirmation to acustomer/subscriber at the service address, wherein the deliveryconfirmation includes the delivery tracking number and the deliveryimage data. In this fashion, the customer can review the delivery imagedata as part of the delivery confirmation to confirm that the packagewas delivered to his or her address and further to determine thelocation of the package delivery at the service address.

FIG. 9 presents a graphical representation of screen display 340 inaccordance with an embodiment of the present disclosure. In particular,a screen display 340 of user interface 142 of client device 100 ispresented as generated by the delivery data client application 150 inresponse to delivery data from the delivery data server application 250.Common elements from other figures may be indicated by common referencenumerals. The screen display 340 is one in a number of different screendisplays relating to deliveries to a particular service address.

In this example, the delivery data includes the captured image data fromthe delivery device 600 corresponding to the delivery. This capturedimage data is sent to the client device 100 from the delivery dataserver 25 in conjunction with a delivery confirmation. When the user BobRobertson logs in to his account at the delivery data server 25, thedelivery confirmation is presented including the tracking number inregion 348 and the captured image data 344 corresponding to the delivery

FIG. 10 presents a graphical representation of screen display 350 inaccordance with an embodiment of the present disclosure. In particular,a screen display 350 of user interface 142 of client device 100 ispresented as generated by an electronic messaging application inresponse to delivery data from the delivery data server application 250or the delivery device 600. Common elements from other figures may beindicated by common reference numerals.

In this example, the delivery data server 25 or the delivery device 600sends an electronic message to the client device 100 that includescaptured image data corresponding to the delivery in conjunction with adelivery confirmation. The electronic message, such as a media message,email, social media message, text message or other electronic messageincludes the captured image data from the delivery device 600corresponding to the delivery. When the user Bob Robertson logs in tohis electronic messaging service or otherwise accesses his electronicmessages, the electronic message containing the delivery confirmation ispresented including the tracking number and the captured image data 354corresponding to the delivery.

FIG. 11 presents a schematic representation of delivery drone 1100 inaccordance with an embodiment of the present disclosure. While the priordisclosure has focused on deliveries by service personnel, many of theprior techniques apply to deliveries by a drone delivery device 1100such as a drone aircraft 1100, autonomous road vehicle or combinationthereof. In particular, delivery location data created by a subscriberthat identifies a delivery location at a service address can be sent viaa network to a drone delivery device 1100 that delivers packages andother goods to the service address. In operation, the drone deliverydevice 1100 locates the delivery location based on the delivery locationdata.

The use of a drone delivery device 1100 easily permits use of a deliverylocation at a backyard location associated with a residential addressthat may be behind a gate, in a locked area or otherwise to areas thatmay be more secure than other delivery locations and/or may not bereadily available to traditional service persons. In addition, the dronedelivery devices can optionally be configured to capture image datacorresponding to the delivery that can be used in conjunction with adelivery confirmation as presented in conjunction with FIGS. 9 and 10.

In an embodiment, the network interface 120 includes a transceiver thatincludes a 802.11x or other wireless local area network (WLAN)transceiver that communicates with an access point (AP) associated withthe service address. In one mode of operation, the subscriber providesthe system identification and/or password associated with the AP. Whenthe delivery drone 1100 comes in range of the AP, it associates with theAP for bidirectional communications with a customer client device 13 or14 via the AP such as communications relating to the particular deliverybeing attempted by the drone delivery device, status communicationsindicating that delivery is in progress, that delivery has been made,direct communication of delivery image data captured after the deliveryby the drone delivery device, prompts for a signature confirmation,receipt of a delivery confirmation and other communications. While thesebidirectional communications are described above in conjunction with alocal area network, other network communications such text messages,instant messages, email messages or other electronic messaging via acellular data network or other wireless networks, with or without theInternet can also be employed.

FIG. 12 presents a block diagram representation of delivery drone 1100in accordance with an embodiment of the present disclosure. The dronedelivery device 1100 includes many common functions and features ofclient device 100 and delivery device 600 described in conjunction withFIG. 3 that are referred to by common reference numerals. In particular,a drone delivery device 1100 is presented for use by delivery servicepersonnel (the user) in conjunction with a delivery of a package orother goods.

The drone delivery device 1100 includes a network interface 120 havingone or more interfaces (122, 124 . . . ). Examples of interfaces (122,124 . . . ) include wireless interfaces such as a 3G, 4G or otherwireless telephony transceiver, a Bluetooth transceiver, a WiFitransceiver, UltraWideBand transceiver, WIMAX transceiver, ZigBeetransceiver or other wireless interface. Examples of interfaces (122,124 . . . ) further include wired interfaces such as a Universal SerialBus (USB) interface, an IEEE 1394 Firewire interface, an Ethernetinterface or other network card or modem for communicating with deliverydata server 25, or other servers such as content servers 12 via network15.

The drone delivery device 1100 also includes a user interface 142 suchas a display device, touch screen, key pad, touch pad, thumb wheel, oneor more buttons, a speaker, a microphone, an accelerometer, gyroscope orother motion or position sensor, or other interface devices that provideinformation to a user of the drone delivery device 1100 such as one ormore service persons and that generate data in response to the user'sinteraction with the drone delivery device 1100. It should be noted,that while the user interface 142 is shown as integrated in the dronedelivery device 1100, the user interface 142 could be a separate unitthat is coupled to the drone delivery device 1100 via network interface120. In this fashion, a smartphone, tablet, personal computer ordedicated device could serve as a user interface 142 for the dronedelivery device 1100 to upload programming, route information,destination information and/or other commands and further to downloaddata such as a delivery image data containing delivery images, routetracking information and other data.

In addition, the drone delivery device 1100 includes an image capturedevice such as a digital camera that captures still or video images withor without associated audio. This image capture device can be used bythe drone delivery device 1100 to capture delivery image data used in adelivery confirmation, to provide visual feedback to the drone deliverydevice 1100 to assist in locating the delivery location, to assist thedrone delivery device 1100 in obstacle avoidance including the avoidanceof in-flight obstacles and determination of whether or not the deliverylocation is free of obstacles such as people, pets, debris or otherobstacles for delivery of the package or other goods to the deliverylocation.

The drone delivery device 1100 also includes a processing module 130 andmemory module 140 that stores an operating system 44 such as aLinux-based operating system, a Microsoft personal computer or mobileoperating system, an Android operating system, an Apple mobile orpersonal computer operating system or other operating system. The memorymodule 140 also stores location data 42 corresponding to the location ofthe drone delivery device 1100 via optional Global Positioning System(GPS) receiver 144 and/or other motion sensors such as an accelerometer,gyroscope, ultrasonic position sensor, altimeter or other sensor, orgathered via a wireless network such as triangulation data received froma 4G network, location information from a connected access point or basestation, femtocell or other location data.

In addition, memory module 140 includes a messaging application 46 forcommunicating with client devices, delivery devices 600 or other dronedelivery devices 1100 such as an email application, a text, instantmessaging or short messaging service (SMS) application or othermessaging application that stores contacts data corresponding tocustomers, service persons and other users associated with a dronedelivery service.

The flight and delivery module 1102 includes a controllable liftmechanism such as a plurality of rotors and flight controls forcontrolling the flight of the drone delivery device 1100 to effectuate adelivery. In addition, the flight and delivery module includes acontrollable package bay or other grasping mechanism to hold a packageor other good during flight and to disengage the package or good whenthe drone delivery device 1100 arrives at the delivery location.

The memory module 140 also stores a delivery application 650 that isprestored in the memory module, loaded via disk or downloaded to thememory module via network interface 120. The processing module 130executes the delivery application 650 to bidirectionally communicatedelivery data with a delivery data server 25 via the network interface120. In addition to receiving delivery location data from delivery dataserver 25 that was generated via interactions with a client device 100,the drone delivery device 1100 can exchange other delivery data withdelivery data server 25 for facilitating deliveries to different serviceaddresses.

The processing module 130 can be implemented via a single processingdevice or a plurality of processing devices. Such processing devices caninclude a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on operational instructions that arestored in a memory of memory module 140. The memory can include a harddisc drive or other disc drive, read-only memory, random access memory,volatile memory, non-volatile memory, static memory, dynamic memory,flash memory, cache memory, and/or any device that stores digitalinformation. Note that when the processing device implements one or moreof its functions via a state machine, analog circuitry, digitalcircuitry, and/or logic circuitry, the memory storing the correspondingoperational instructions may be embedded within, or external to, thecircuitry comprising the state machine, analog circuitry, digitalcircuitry, and/or logic circuitry. While a particular bus architectureis presented that includes a single bus 160, other architectures arepossible including additional data buses and/or direct connectivitybetween one or more elements. Further, the drone delivery device 1100can include one or more additional elements that are not specificallyshown.

In an embodiment, the delivery data received from the delivery dataserver 25 includes delivery location data generated by a client devicethat indicates a service address associated with a user of the clientdevice and a delivery location associated with the service address forreceiving at least one delivery to the service address. As previouslydiscussed, the delivery location data can indicates a user selection ofthe delivery location in relation to captured image data correspondingto the delivery address. The delivery location data can include aservice address, GPS coordinate of the delivery location at the serviceaddress and/or the captured image data of the delivery location. In onemode of operation, the drone delivery device 1100 can use the serviceaddress and or GPS coordinates initially to locate the vicinity of thedelivery location. When in the vicinity of the delivery location, theimage capture device 146 can be used by the drone delivery device 1100in conjunction with the captured image data corresponding to thedelivery address to aid the drone delivery device 1100 in identifyingthe location at the service address to place the package or otherdelivery.

In another mode of operation, the image capture device 146 of the dronedelivery device 1100 generates delivery image data of a delivery of thepackage or other goods at a service address. After delivery, the dronedelivery device 1100 orients itself, such as by recognizing capturedimage data relating to the package or goods that were just delivered, totake a picture of the package or other goods at the actual deliverylocation. The memory stores the delivery image data. The delivery dataincludes a delivery tracking number for a particular delivery along withthe delivery image data. The delivery data server 25 receives thedelivery data and processes the delivery data to provide a deliveryconfirmation to a customer at the service address that includes thedelivery tracking number and the delivery image data.

FIG. 13 presents a graphical representation of screen display 360 inaccordance with an embodiment of the present disclosure. In particular,a screen display 360 of user interface 142 of client device 100 ispresented as generated by an electronic messaging application inresponse to delivery data. Common elements from other figures may beindicated by common reference numerals.

In this example, the delivery data server 25 or the drone deliverydevice 1100 sends an electronic message to the client device 100 thatincludes captured image data corresponding to the delivery inconjunction with a delivery confirmation. The electronic message, suchas a media message, email, social media message, text message or otherelectronic message includes the captured image data from the dronedelivery device 1100 corresponding to the delivery. When the user BobRobertson logs in to his electronic messaging service or otherwiseaccesses his electronic messages, the electronic message containing thedelivery confirmation is presented including the tracking number and thecaptured image data 364 corresponding to the delivery.

It should be noted, that while the delivery confirmation correspondingto the drone delivery of the package 354 is presented in conjunctionwith an electronic message, the captured image data 364 could likewisebe conveyed in other ways including by access to the subscriber'saccount via delivery data server 25 as described in conjunction withFIG. 9.

FIG. 14 presents a pictorial representation of delivery mat 1400 inaccordance with an embodiment of the present disclosure. In particular adelivery mat 1400 is presented for use in conjunction with a dronedelivery device 1100 or other delivery drone.

In this embodiment, the delivery mat 1400 is provided to a customer toreceive one or more drone deliveries. The user places the delivery matin a desired delivery location at their service address. The deliverymat 1400 includes a visible landing target that can be used by a dronedelivery device 1100 or other delivery drone to more precisely locatethe delivery location at the service address.

As previously discussed, delivery location data provided to the dronedelivery device 1100 can include a service address and/or GPScoordinates of the delivery location at the service address. In one modeof operation, the drone delivery device 1100 can use the service addressand or GPS coordinates initially to locate the vicinity of the deliverylocation. When in the vicinity of the delivery location, the imagecapture device 146 can be used by the drone delivery device 1100 to aidthe drone delivery device 1100 in identifying the location at theservice address to place the package or other delivery. In particular,image recognition performed via the delivery application 650 canrecognize the presence or absence of the delivery target in a capturedfield of view and further can be used in a pattern search or othersearch to locate the delivery mat and further to home in on the locationof the delivery mat.

FIG. 15 presents a pictorial representation of delivery mat 1500 inaccordance with an embodiment of the present disclosure. In particular adelivery mat 1500 is presented for use in conjunction with a dronedelivery device 1100 or other delivery drone.

In this embodiment, the delivery mat 1500 is provided to a customer toreceive one or more drone deliveries. The user places the delivery matin a desired delivery location at their service address. The deliverymat 1500 includes a visible landing target that can be used by a dronedelivery device 1100 or other delivery drone to more precisely locatethe delivery location at the service address. The visible landing targetincludes a visible two-dimensional code such as a bar code or othertwo-dimensional code that uniquely identifies the subscriber.

As previously discussed, delivery location data provided to the dronedelivery device 1100 can include a service address and/or GPScoordinates of the delivery location at the service address. In one modeof operation, the drone delivery device 1100 can use the service addressand or GPS coordinates initially to locate the vicinity of the deliverylocation. When in the vicinity of the delivery location, the imagecapture device 146 can be used by the drone delivery device 1100 to aidthe drone delivery device 1100 in identifying the location at theservice address to place the package or other delivery. In particular,image recognition performed via the delivery application 650 canrecognize the presence or absence of the delivery target in a capturedfield of view and further can be used in a pattern search or othersearch to locate the delivery mat. The drone delivery device 1100 canconfirm the association of the package or goods to be delivered with theparticular delivery mat by recognizing the two-dimensional code andassociating the two-dimensional code with either the particular deliveryor the subscriber and, when recognized, visually homing in on thelocation of the delivery mat.

FIG. 16 presents a block diagram representation of beacon device 1600 inaccordance with an embodiment of the present disclosure. In particular abeacon device 1600 is presented for use in conjunction with a dronedelivery device 1100 or other delivery drone.

In this embodiment, the beacon device 1600 is provided to a customer toreceive one or more drone deliveries. The user places the beacon device1600 in a desired delivery location at their service address. The beacondevice 1600 generates a visible beacon 1630 that can be used by a dronedelivery device 1100 or other delivery drone to more precisely locatethe delivery location at the service address.

The beacon device includes a beacon code generator 1610 that generatesbeacon data 1602 that uniquely indicates a subscriber. The beacongenerator generates a wireless homing beacon, such as visual beacon 1630that indicates the beacon data 1602. The wireless homing beacon 1630 isdetectable by the drone delivery device to facilitate a service deliveryby the drone delivery device at the location of the beacon device 1600.

In an embodiment, the visual beacon 1630 is a visible signal, such as avisible light wave, a near infrared light wave, in infrared beacon orother visible or non-visible signal that is modulated via the beacondata 1602 and that can be optically detected via an image capturedevice, such as image capture device 146. The beacon code generator 1610can includes a linear feedback shift register that generates a pseudorandom code sequence that is unique to the subscriber or pseudo-unique.The beacon data 1602 includes the pseudo random code sequence that isrecognized by the drone delivery device for authentication with eitherthe delivery or the delivery customer. In another configuration, thebeacon code generator 1610 includes a security token module thatgenerates a rolling sequence of encryption codes. The beacon data 1602includes the rolling sequence of encryption codes that is recognized bythe drone delivery device for authentication with either the delivery orthe delivery customer. In a further configuration the beacon data 1602includes a low density parity check code that is recognized by the dronedelivery device for authentication with either the delivery or thedelivery customer.

As previously discussed, delivery location data provided to the dronedelivery device 1100 can include a service address and/or GPScoordinates of the delivery location at the service address. In one modeof operation, the drone delivery device 1100 can use the service addressand or GPS coordinates initially to locate the vicinity of the deliverylocation. When in the vicinity of the delivery location, the imagecapture device 146 can be used by the drone delivery device 1100 to aidthe drone delivery device 1100 in identifying the location at theservice address to place the package or other delivery. In particular,image recognition performed via the delivery application 650 canrecognize the presence or absence of the visual beacon 1630 in acaptured field of view and further can be used in a pattern search orother search to locate the visual beacon 1630. The drone delivery device1100 can confirm the association of the package or goods to be deliveredwith the particular visual beacon 1630 by authenticating the subscriberor delivery based on extracting the beacon data 1602 via demodulation.When the visual beacon 1630 is recognized, the delivery drone 1100 canvisually home in on the location of the beacon device 1600.

It should be noted that the beacon device 1600 can be used with orwithout a delivery mat such as delivery mat 1400 or 1500. When employed,the location of delivery mat 1400 or 1500 can be used in conjunctionwith the beacon device 1600 to more precisely determine the deliverylocation and indicate the spot where the package or other goods shouldbe placed in the vicinity of the beacon device 1600.

FIG. 17 presents a block diagram representation of beacon device 1700 inaccordance with an embodiment of the present disclosure. In particular abeacon device 1700 is presented for use in conjunction with a dronedelivery device 1100 or other delivery drone.

In this embodiment, the beacon device 1700 is provided to a customer toreceive one or more drone deliveries. The user places the beacon device1700 in a desired delivery location at their service address. The beacondevice 1700 generates a radio frequency (RF) beacon 1730 that can beused by a drone delivery device 1100 or other delivery drone to moreprecisely locate the delivery location at the service address.

The beacon device includes a beacon code generator 1610 that generatesbeacon data 1602 that uniquely indicates a subscriber. The beacongenerator generates a wireless homing beacon, such as RF beacon 1730that indicates the beacon data 1602. The wireless homing beacon isdetectable by the drone delivery device to facilitate a service deliveryby the drone delivery device at the location of the beacon device 1700.

In an embodiment, the beacon code generator 1610 can includes a linearfeedback shift register that generates a pseudo random code sequencethat is unique to the subscriber or pseudo-unique. The beacon data 1602includes the pseudo random code sequence that is recognized by the dronedelivery device for authentication with either the delivery or thedelivery customer. In another configuration, the beacon code generator1610 includes a security token module that generates a rolling sequenceof encryption codes. The beacon data 1602 includes the rolling sequenceof encryption codes that is recognized by the drone delivery device forauthentication with either the delivery or the delivery customer. In afurther configuration the beacon data 1602 includes a low density paritycheck code that is recognized by the drone delivery device forauthentication with either the delivery or the delivery customer.

As previously discussed, delivery location data provided to the dronedelivery device 1100 can include a service address and/or GPScoordinates of the delivery location at the service address. In one modeof operation, the drone delivery device 1100 can use the service addressand or GPS coordinates initially to locate the vicinity of the deliverylocation. When in the vicinity of the delivery location, the imagecapture device 146 can be used by the drone delivery device 1100 to aidthe drone delivery device 1100 in identifying the location at theservice address to place the package or other delivery. In particular,an RF receiver or transceiver included in the delivery device can beused to receive the RF beacon 1730. In an embodiment, the RF receiver ortransceiver generates a signal strength indication and a directionalbeam antenna that can be used by the drone delivery device 1100 toestimate the distance and direction to the beacon device 1700. The dronedelivery device 1100 can confirm the association of the package or goodsto be delivered with the particular RF beacon 1730 by authenticating thesubscriber or delivery based on extracting the beacon data 1602 viademodulation. When the RF beacon 1730 is recognized, the delivery drone1100 can home in on the location of the beacon device 1700.

It should be noted that the beacon device 1700 can be used with orwithout a delivery mat such as delivery mat 1400 or 1500. When employed,the location of delivery mat 1400 or 1500 can be used in conjunctionwith the beacon device 1700 to more precisely determine the deliverylocation and indicate the spot where the package or other goods shouldbe placed in the vicinity of the beacon device 1700.

In an embodiment, the RF beacon generator 1620 is implemented via an RFtransceiver that can bidirectionally communicate data with a dronedelivery device such as drone delivery device 1100. In an embodiment,the RF transceiver includes an antenna array or other directionalantenna that can be used to provide directional feedback data to thedrone delivery device to aid in locating the beacon device 1700 by thedrone delivery device. The data communication between the beacon device1700 and the drone delivery device can include packet transmissions andacknowledgements, including handshake signaling, communication to thebeacon device of 1700 relating to the particular delivery beingattempted by the drone delivery device, status communications indicatingthat delivery is in progress, that delivery has been made, directcommunication of delivery image data captured after the delivery by thedrone delivery device and other communications.

The beacon device 1700 optionally contains a network interface 120 thatpermits the beacon device 1700 to communicate with thesubscriber/customer. For example, the network interface can include awireless local area network transceiver such as an 802.11a,b,g,n,ac . .. (802.11x) compatible device that is associated with an access point atthe customer premises. In this fashion, status communications indicatingthat delivery is in progress, that delivery has been made, directcommunication of delivery image data captured after the delivery by thedrone delivery device and other communications can be sent directly viaelectronic messaging to a client device associated with thesubscriber/customer.

FIG. 18 presents a pictorial representation of street view 1800 inaccordance with an embodiment of the present disclosure. In thisembodiment, a beacon device 1600 or 1700 is provided to a customer toreceive one or more drone deliveries. The user places the beacon device1600 or 1700 in a desired delivery location at their service address.The beacon device 1600 or 1700 generates a wireless beacon that can beused by a drone delivery device 1100 or other delivery drone to moreprecisely locate the delivery location at the service address.

As discussed in conjunction with FIGS. 16 and 17, the beacon device 1600or 1700 can be used with or without a delivery mat such as delivery mat1400 or 1500. When employed, the location of delivery mat 1400 or 1500can be used in conjunction with the beacon device 1600 or 1700 to moreprecisely determine the delivery location and indicate the spot wherethe package or other goods should be placed in the vicinity of thebeacon device 1600 or 1700.

FIG. 19 presents a block diagram representation of delivery drone 1100in accordance with another embodiment of the present disclosure. Adelivery drone is presented that includes similar elements described inconjunction with FIGS. 1-18 that are referred to by common referencenumerals. In addition, interface 1920 includes interface 122, 124 . . .and a RF transceiver 1922 for receiving and demodulating the RF beacon1730 and/or communicating with beacon device 1700.

In the embodiment, RF transceiver 1922 can bidirectionally communicatedata with a beacon device 1700 or other communication device at thepremises of the service address. The data communication between thebeacon device 1700 and the drone delivery device 1100 can include packettransmissions and acknowledgements, including handshake signaling,communication to the beacon device of 1700 relating to the particulardelivery being attempted by the drone delivery device, statuscommunications indicating that delivery is in progress, that deliveryhas been made, direct communication of delivery image data capturedafter the delivery by the drone delivery device and othercommunications. In a mode of operation, the drone delivery device 1100communicates with a customer at the service address to prompt thecustomer for a real-time signature confirmation and receives thereal-time signature confirmation from the customer as a conditionprecedent to completing the delivery.

In an embodiment, the RF transceiver 1922 of other transceiver thatincludes a 802.11x or other WLAN transceiver that communicates with anaccess point (AP) associated with the either the beacon device 1700 orotherwise with the service address. In one mode of operation, thesubscriber provides the system identification and/or password associatedwith the AP. When the delivery drone 1100 comes in range of the AP, itassociates with the AP for bidirectional communications with a clientdevice 100 of the customer/subscriber via the AP such as communicationsrelating to the particular delivery being attempted by the dronedelivery device, status communications indicating that delivery is inprogress, that delivery has been made, direct communication of deliveryimage data captured after the delivery by the drone delivery device,prompts for a signature confirmation, receipt of a delivery confirmationand other communications.

FIG. 20 presents a graphical representation of screen display 2000 inaccordance with an embodiment of the present disclosure. In particular,a screen display 2000 of user interface 142 of client device 100 ispresented as generated by the delivery data client application 150 inresponse to delivery data from the delivery data server application 250.Common elements from other figures may be indicated by common referencenumerals. The screen display 2000 is one in a number of different screendisplays that guide the user in entering delivery data relating todeliveries to a particular service address.

Delivery location data received from the client device 100 is generatedat the client device 100 based on a user selection of the deliverylocation at the service address based on captured GPS coordinates. Inthis embodiment, the user of the client device 100 takes the clientdevice to the delivery location. The GPS receiver 144 generates GPScoordinates that are displayed in region 2004 of the display based onthe operation of delivery data client application 150. In addition,delivery data client application 150 displays a map view 2002 of theimmediate area based on map data stored on the client device 100 orreceived via delivery data server 25 and/or a content server 12 thatcontains a map database. The map data can include satellite imagery,street views, virtual maps, or other maps. The current location of theclient device 100 indicated by the GPS coordinates can be indicated bythe pin indicator 2010 or other indicator. The delivery location data issent to the delivery data server 25. The delivery data serverapplication 250 processes the delivery location data to direct one ormore deliveries to the service address. In particular captured imagedata and/or other delivery location data can be used by deliverypersonnel to place a delivery in a desired delivery location.

While the example described above has focused on a street view, othermap views of the property at the delivery address can likewise beemployed. In another example, a sky view is either retrieved from adatabase 246 of the delivery data server 25 or from a content server 12that provides captured image data, such as satellite or drone imageryfor different street addresses.

FIG. 21 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure. In particular, a method ispresented for use with one or more of the functions and featuresdescribed in conjunction with FIGS. 1-20. Step 400 includes sendingdelivery menu data from the delivery data server sent to the firstclient device via a network. Step 402 includes receiving deliverylocation data at the delivery data server from the first client devicethat indicates a service address associated with a user of the firstclient device and a delivery location associated with the serviceaddress for receiving at least one delivery to the service address,wherein the delivery location data is generated at the first clientdevice based on a user selection of the delivery location in relation tothe captured image data corresponding to the delivery address. Step 404includes processing the delivery location data at the delivery dataserver to direct the at least one delivery to the service address.

In an embodiment, the first client device generates the deliverylocation in relation to the captured image data corresponding to thedelivery address based on a superposition of a delivery location icon onthe captured image data corresponding to the delivery address. Thedelivery location data can include the superposition of the deliverylocation icon on the captured image data corresponding to the deliveryaddress. The delivery location data can be sent to a delivery deviceassociated with a delivery service person and wherein the deliverydevice displays the superposition of the delivery location icon on thecaptured image data corresponding to the delivery address. The capturedimage data corresponding to the delivery address can represent at leastone of: a street view corresponding to the delivery address, and a skyview corresponding to the delivery address. The delivery location datacan include GPS coordinates selected by the first client device. Thedelivery location data can be sent via the network to a drone deliverydevice that locates the delivery location based on the delivery locationdata. The service address can be a residential address and the deliverylocation associated with the service address can corresponds to abackyard location associated with the residential address.

FIG. 22 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure. In particular, a method ispresented for use with one or more of the functions and featuresdescribed in conjunction with FIGS. 1-21. Step 410 includes capturingimage data corresponding to the at least one delivery via a deliverydevice. Step 412 includes sending the image data corresponding to the atleast one delivery to the first client device in conjunction with adelivery confirmation. In an embodiment, the delivery confirmation issent to the first client device via an electronic message that includesthe image data corresponding to the at least one delivery.

FIG. 23 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure. In particular, a method ispresented for use with one or more of the functions and featuresdescribed in conjunction with FIGS. 1-22. Step 420 includes generatingdelivery image data of a delivery at a service address via an imagecapture device. Step 422 includes sending the delivery image data of thedelivery at the service address and the tracking number to the deliverydata server, wherein the delivery data server processes the deliverydata to provide a delivery confirmation to a customer at the serviceaddress, wherein the delivery confirmation includes the deliverytracking number and the delivery image data.

FIG. 24 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure. In particular, a method ispresented for use with one or more of the functions and featuresdescribed in conjunction with FIGS. 1-23. Step 430 includes receivingdelivery location data generated by a client device that indicates aservice address associated with a user of the client device and adelivery location associated with the service address for receiving atleast one delivery to the service address.

FIG. 25 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure. In particular, a method ispresented for use with one or more of the functions and featuresdescribed in conjunction with FIGS. 1-24. Step 440 includes displayingthe captured image data corresponding to the delivery address on adisplay device of the delivery device.

In an embodiment, the delivery location data indicates the userselection of the delivery location by superposition of a deliverylocation icon on the captured image data corresponding to the deliveryaddress, and the display device displays the superposition of thedelivery location icon on the captured image data corresponding to thedelivery address. The captured image data corresponding to the deliveryaddress can include at least one of: a street view corresponding to thedelivery address, and a sky view corresponding to the delivery address.

FIG. 26 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure. In particular, a method ispresented for use with one or more of the functions and featuresdescribed in conjunction with FIGS. 1-25. Step 450 includes capturing alive image corresponding to the delivery address. Step 452 includessuperimposing a delivery location icon on the live image correspondingto the delivery address, wherein a position of the delivery locationicon on the live image is adjusted to correspond to the deliverylocation.

FIG. 27 presents a flowchart representation of a method in accordancewith an embodiment of the present disclosure. In particular, a method ispresented for use with one or more of the functions and featuresdescribed in conjunction with FIGS. 1-26. Step 460 includes generatingbeacon data that uniquely indicates a subscriber. Step 462 includesgenerating a wireless homing beacon that indicates the beacon data,wherein the wireless homing beacon is detectable by the at least onedrone delivery device to facilitate a service delivery by the dronedelivery device at the location of the beacon device.

In an embodiment, generating the beacon data includes generating apseudo random code sequence and wherein the beacon data includes thepseudo random code sequence. The beacon data can also, or in thealternative, include a rolling sequence of encryption codes and/or a lowdensity parity check code.

In embodiments, the wireless homing beacon includes an infrared signalmodulated via the beacon data, a visible signal modulated via the beacondata, and/or a radio frequency signal modulated via the beacon data.

The method can further include providing a delivery mat. The deliverymat can include a visible landing target and/or a visibletwo-dimensional code that uniquely indicates the subscriber.

It is noted that digital information whose content corresponds to any ofa number of desired types (e.g., data, video, speech, audio, etc.) maygenerally be referred to as ‘media’ or ‘data’.

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. Such an industry-accepted toleranceranges from less than one percent to fifty percent and corresponds to,but is not limited to, component values, integrated circuit processvariations, temperature variations, rise and fall times, and/or thermalnoise. Such relativity between items ranges from a difference of a fewpercent to magnitude differences. As may also be used herein, theterm(s) “configured to”, “operably coupled to”, “coupled to”, and/or“coupling” includes direct coupling between items and/or indirectcoupling between items via an intervening item (e.g., an item includes,but is not limited to, a component, an element, a circuit, and/or amodule) where, for an example of indirect coupling, the intervening itemdoes not modify the information of a signal but may adjust its currentlevel, voltage level, and/or power level. As may further be used herein,inferred coupling (i.e., where one element is coupled to another elementby inference) includes direct and indirect coupling between two items inthe same manner as “coupled to”. As may even further be used herein, theterm “configured to”, “operable to”, “coupled to”, or “operably coupledto” indicates that an item includes one or more of power connections,input(s), output(s), etc., to perform, when activated, one or more itscorresponding functions and may further include inferred coupling to oneor more other items. As may still further be used herein, the term“associated with”, includes direct and/or indirect coupling of separateitems and/or one item being embedded within another item.

As may also be used herein, the terms “processing module”, “processingcircuit”, “processor”, and/or “processing unit” may be a singleprocessing device or a plurality of processing devices. Such aprocessing device may be a microprocessor, micro-controller, digitalsignal processor, microcomputer, central processing unit, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on hard coding of thecircuitry and/or operational instructions. The processing module,module, processing circuit, and/or processing unit may be, or furtherinclude, memory and/or an integrated memory element, which may be asingle memory device, a plurality of memory devices, and/or embeddedcircuitry of another processing module, module, processing circuit,and/or processing unit. Such a memory device may be a read-only memory,random access memory, volatile memory, non-volatile memory, staticmemory, dynamic memory, flash memory, cache memory, and/or any devicethat stores digital information. Note that if the processing module,module, processing circuit, and/or processing unit includes more thanone processing device, the processing devices may be centrally located(e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that if the processing module, module, processing circuit,and/or processing unit implements one or more of its functions via astate machine, analog circuitry, digital circuitry, and/or logiccircuitry, the memory and/or memory element storing the correspondingoperational instructions may be embedded within, or external to, thecircuitry comprising the state machine, analog circuitry, digitalcircuitry, and/or logic circuitry. Still further note that, the memoryelement may store, and the processing module, module, processingcircuit, and/or processing unit executes, hard coded and/or operationalinstructions corresponding to at least some of the steps and/orfunctions illustrated in one or more of the Figures. Such a memorydevice or memory element can be included in an article of manufacture.

One or more embodiments have been described above with the aid of methodsteps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claims. Further, the boundariesof these functional building blocks have been arbitrarily defined forconvenience of description. Alternate boundaries could be defined aslong as the certain significant functions are appropriately performed.Similarly, flow diagram blocks may also have been arbitrarily definedherein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence couldhave been defined otherwise and still perform the certain significantfunctionality. Such alternate definitions of both functional buildingblocks and flow diagram blocks and sequences are thus within the scopeand spirit of the claims. One of average skill in the art will alsorecognize that the functional building blocks, and other illustrativeblocks, modules and components herein, can be implemented as illustratedor by discrete components, application specific integrated circuits,processors executing appropriate software and the like or anycombination thereof.

In addition, a flow diagram may include a “start” and/or “continue”indication. The “start” and “continue” indications reflect that thesteps presented can optionally be incorporated in or otherwise used inconjunction with other routines. In this context, “start” indicates thebeginning of the first step presented and may be preceded by otheractivities not specifically shown. Further, the “continue” indicationreflects that the steps presented may be performed multiple times and/ormay be succeeded by other by other activities not specifically shown.Further, while a flow diagram indicates a particular ordering of steps,other orderings are likewise possible provided that the principles ofcausality are maintained.

The one or more embodiments are used herein to illustrate one or moreaspects, one or more features, one or more concepts, and/or one or moreexamples. A physical embodiment of an apparatus, an article ofmanufacture, a machine, and/or of a process may include one or more ofthe aspects, features, concepts, examples, etc. described with referenceto one or more of the embodiments discussed herein. Further, from figureto figure, the embodiments may incorporate the same or similarly namedfunctions, steps, modules, etc. that may use the same or differentreference numbers and, as such, the functions, steps, modules, etc. maybe the same or similar functions, steps, modules, etc. or differentones.

Unless specifically stated to the contra, signals to, from, and/orbetween elements in a figure of any of the figures presented herein maybe analog or digital, continuous time or discrete time, and single-endedor differential. For instance, if a signal path is shown as asingle-ended path, it also represents a differential signal path.Similarly, if a signal path is shown as a differential path, it alsorepresents a single-ended signal path. While one or more particulararchitectures are described herein, other architectures can likewise beimplemented that use one or more data buses not expressly shown, directconnectivity between elements, and/or indirect coupling between otherelements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of theembodiments. A module implements one or more functions via a device suchas a processor or other processing device or other hardware that mayinclude or operate in association with a memory that stores operationalinstructions. A module may operate independently and/or in conjunctionwith software and/or firmware. As also used herein, a module may containone or more sub-modules, each of which may be one or more modules.

While particular combinations of various functions and features of theone or more embodiments have been expressly described herein, othercombinations of these features and functions are likewise possible. Thepresent disclosure is not limited by the particular examples disclosedherein and expressly incorporates these other combinations.

What is claimed is:
 1. A system comprising: a delivery devicecomprising: a network interface for communicating via a network; animage capture device for generating delivery image data of a delivery ata service address; a memory that stores a delivery application and thedelivery image data; a processing module, coupled to the memory and thenetwork interface, the processing module including at least oneprocessor that executes the delivery application to bidirectionallycommunicate delivery data with a delivery data server via the networkinterface, wherein the delivery data includes a delivery tracking numberand the delivery image data; the delivery data server configured to:receive the delivery data; and process the delivery data to provide adelivery confirmation to a customer at the service address, wherein thedelivery confirmation includes the delivery tracking number and thedelivery image data.
 2. The system of claim 1 wherein the networkinterface receives delivery location data generated by a client devicethat indicates a service address associated with a user of the clientdevice and a delivery location associated with the service address forreceiving at least one delivery to the service address.
 3. The system ofclaim 2 wherein the delivery location data indicates a user selection ofthe delivery location in relation to captured image data correspondingto the delivery address.
 4. The system of claim 3 wherein the deliverylocation data indicates the user selection of the delivery location bysuperposition of a delivery location icon on the captured image datacorresponding to the delivery address.
 5. The system of claim 4 furthercomprising: a display device that displays the superposition of thedelivery location icon on the captured image data corresponding to thedelivery address.
 6. The system of claim 5 wherein the captured imagedata corresponding to the delivery address includes to at least one of:a street view corresponding to the delivery address, and a sky viewcorresponding to the delivery address.
 7. The system of claim 2 furthercomprising: a display device, coupled to the processing module, thatdisplays a superposition of a delivery location icon on a live imagecorresponding to the delivery address, wherein a position of thedelivery location icon on the live image is adjusted to correspond tothe delivery location and wherein the live image is generated by theimage capture device.
 8. A delivery device for use with a delivery dataserver comprising: a network interface for communicating via a network;an image capture device for generating delivery image data of a deliveryat a service address; a memory that stores a delivery application andthe delivery image data; and a processing module, coupled to the memoryand the network interface, the processing module including at least oneprocessor that executes the delivery application to bidirectionallycommunicate delivery data with the delivery data server via the networkinterface, wherein the delivery data includes a delivery tracking numberand the delivery image data; wherein the delivery data server processesthe delivery data to provide a delivery confirmation to a customer atthe service address, wherein the delivery confirmation includes thedelivery tracking number and the delivery image data.
 9. The deliverydevice of claim 8 wherein the network interface receives deliverylocation data generated by a client device that indicates a serviceaddress associated with a user of the client device and a deliverylocation associated with the service address for receiving at least onedelivery to the service address.
 10. The delivery device of claim 9wherein the delivery location data indicates a user selection of thedelivery location in relation to captured image data corresponding tothe delivery address.
 11. The delivery device of claim 10 wherein thedelivery location data indicates the user selection of the deliverylocation by superposition of a delivery location icon on the capturedimage data corresponding to the delivery address.
 12. The deliverydevice of claim 11 further comprising: a display device that displaysthe superposition of the delivery location icon on the captured imagedata corresponding to the delivery address.
 13. The delivery device ofclaim 12 wherein the captured image data corresponding to the deliveryaddress includes to at least one of: a street view corresponding to thedelivery address, and a sky view corresponding to the delivery address.14. The delivery device of claim 9 further comprising: a display device,coupled to the processing module, that displays a superposition of adelivery location icon on a live image corresponding to the deliveryaddress, wherein a position of the delivery location icon on the liveimage is adjusted to correspond to the delivery location and wherein thelive image is generated by the image capture device.
 15. A method foruse with a delivery device and a delivery data server, the methodcomprising: generating delivery image data of a delivery at a serviceaddress via an image capture device; and sending the delivery image dataof the delivery at the service address and a tracking number to thedelivery data server; wherein the delivery data server processes thedelivery data to provide a delivery confirmation to a customer at theservice address, wherein the delivery confirmation includes the deliverytracking number and the delivery image data.
 16. The method of claim 15further comprising: receiving delivery location data generated by aclient device that indicates the service address associated with a userof the client device and a delivery location associated with the serviceaddress for receiving at least one delivery to the service address. 17.The method of claim 16 wherein the delivery location data indicates auser selection of the delivery location in relation to captured imagedata corresponding to the delivery address and the method furthercomprises: displaying the captured image data corresponding to thedelivery address on a display device of the delivery device.
 18. Themethod of claim 17 wherein the delivery location data indicates the userselection of the delivery location by superposition of a deliverylocation icon on the captured image data corresponding to the deliveryaddress; and wherein the display device displays the superposition ofthe delivery location icon on the captured image data corresponding tothe delivery address.
 19. The method of claim 17 wherein the capturedimage data corresponding to the delivery address includes at least oneof: a street view corresponding to the delivery address, and a sky viewcorresponding to the delivery address.
 20. The method of claim 15further comprising: capturing a live image corresponding to the deliveryaddress; and superimposing a delivery location icon on the live imagecorresponding to the delivery address, wherein a position of thedelivery location icon on the live image is adjusted to correspond tothe delivery location.